fix(release): use valid semantic-release commit_parser value - #113

Summary

Generate a valid python-semantic-release commit_parser value (conventional) instead of the rejected pre-v10 alias conventional_commits.

Why

Projects generated from this template inherit commit_parser = "conventional_commits", and their Semantic Release workflow fails at the "Python Semantic Release" step (observed on homelab-infra run 36916602542 and rag-processor run 36919561488):

$> /opt/psr/.venv/bin/semantic-release -v version --no-commit --no-vcs-release
[error] Unrecognized commit parser value: 'conventional_commits'.
[error] Invalid import path 'conventional_commits', must use 'module:Class' format

The org reusable python-release.yml pins python-semantic-release v10.6.1, whose built-in parser registry only recognizes angular, conventional, conventional-monorepo, emoji, scipy and tag. At least eight generated repos carry the bad value (homelab-infra, rag-processor, audio-processor, llc-manager, python-libs, maester-tests, AMC, dna); each has its own fix PR.

Changes

• {{cookiecutter.project_slug}}/pyproject.toml: commit_parser = "conventional".
• {{cookiecutter.project_slug}}/.standards/pyproject.toml.baseline: same change in the commented reference line, so cruft/merge-standards stops re-propagating the bad value.
• CLAUDE.md: same change in the documented configuration example.

Test plan

• Rendered the template with cookiecutter --no-input, then ran uvx --from python-semantic-release==10.6.1 semantic-release --noop version --print on the generated project: exits 0 and prints a version. The same project with the old value exits 1 with Unrecognized commit parser value: 'conventional_commits'.
• pre-commit run --files <changed files> passes.
• Required PR checks green.

Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Updated the documented semantic-release commit parser name to conventional.